Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 775ccc249fef546bccf9d00e76f559af43817504c051f1f7ef8b154c945224ac

Tx prefix hash: c0efffb4311cd83ebdfb03409ed93e243c3835687fd465211a8ea7d05d63ba45
Tx public key: 97686b38e4b7d92d376d64e4e5a9a0bf5af1fb0b7235b36129c1efef5b708b44
Timestamp: 1736356269 Timestamp [UCT]: 2025-01-08 17:11:09 Age [y:d:h:m:s]: 00:314:21:01:25
Block: 1193015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222556 RingCT/type: yes/0
Extra: 0197686b38e4b7d92d376d64e4e5a9a0bf5af1fb0b7235b36129c1efef5b708b4402110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 285a6d639d490e461a987fd3550fcdd66216f440760728082ce65fdd641e27e7 0.600000000000 1679572 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": 1193025, "vin": [ { "gen": { "height": 1193015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "285a6d639d490e461a987fd3550fcdd66216f440760728082ce65fdd641e27e7" } } ], "extra": [ 1, 151, 104, 107, 56, 228, 183, 217, 45, 55, 109, 100, 228, 229, 169, 160, 191, 90, 241, 251, 11, 114, 53, 179, 97, 41, 193, 239, 239, 91, 112, 139, 68, 2, 17, 0, 0, 0, 12, 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