Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 488fc18394f311b4e703c72c084968a0d705c4c018c5b6b3f69bd734442056bb

Tx prefix hash: 5210ba4e7f3dd8bbd1b74c31ac69ec7e48205b59c8bdf5b1cfdb3902c025006a
Tx public key: d06914f472dbbcce6cd1a11739e0aa185a164d2bc0e955b5340d8b860877169a
Timestamp: 1747094129 Timestamp [UCT]: 2025-05-12 23:55:29 Age [y:d:h:m:s]: 00:191:19:02:51
Block: 1281642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134788 RingCT/type: yes/0
Extra: 01d06914f472dbbcce6cd1a11739e0aa185a164d2bc0e955b5340d8b860877169a0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 596a6fd24344b662b51466eeb6d9ae7b7bfeed95eb6e76f6b4e1bcf8220d4a6c 0.600000000000 1769041 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": 1281652, "vin": [ { "gen": { "height": 1281642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "596a6fd24344b662b51466eeb6d9ae7b7bfeed95eb6e76f6b4e1bcf8220d4a6c" } } ], "extra": [ 1, 208, 105, 20, 244, 114, 219, 188, 206, 108, 209, 161, 23, 57, 224, 170, 24, 90, 22, 77, 43, 192, 233, 85, 181, 52, 13, 139, 134, 8, 119, 22, 154, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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