Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9ffcf19b6c4cfda374cf7d7d8ec5f1b1068b6f50281d856642aecce85964bbd9

Tx prefix hash: 11d448d26be60360ad897a25acb88fee53a6384e7eecd4b9357d12e50308adc3
Tx public key: 70d2560d9b1831a43c64cba64e8b01a3decd3391e9022199dff8b99a86184fa5
Timestamp: 1731465171 Timestamp [UCT]: 2024-11-13 02:32:51 Age [y:d:h:m:s]: 00:363:02:11:03
Block: 1152504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257055 RingCT/type: yes/0
Extra: 0170d2560d9b1831a43c64cba64e8b01a3decd3391e9022199dff8b99a86184fa50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfce462743ffddc254c30b142a4d5398eb5519ae90312e73a140122f73f5679e 0.600000000000 1638103 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1152514, "vin": [ { "gen": { "height": 1152504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfce462743ffddc254c30b142a4d5398eb5519ae90312e73a140122f73f5679e" } } ], "extra": [ 1, 112, 210, 86, 13, 155, 24, 49, 164, 60, 100, 203, 166, 78, 139, 1, 163, 222, 205, 51, 145, 233, 2, 33, 153, 223, 248, 185, 154, 134, 24, 79, 165, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8