Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a241f3c22426f33c400ec3c78b89549a0a05c3f886533ccb6b3320e62794ede4

Tx prefix hash: dd30234cb07c05b6f1edc6e47e00296c2335c7eea09fcad4ad67bbe8cb4d471f
Tx public key: 3d1469f38d402ea7a50ba5d456f97f279063f90b16aeaf44536e7fc5f13691d1
Timestamp: 1738153833 Timestamp [UCT]: 2025-01-29 12:30:33 Age [y:d:h:m:s]: 00:296:05:19:09
Block: 1207637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209467 RingCT/type: yes/0
Extra: 013d1469f38d402ea7a50ba5d456f97f279063f90b16aeaf44536e7fc5f13691d10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 032a945bd2b3bf9e38654452ef32a00ceb369b4dfb003361bd0fc5a4eb1956c2 0.600000000000 1694362 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": 1207647, "vin": [ { "gen": { "height": 1207637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "032a945bd2b3bf9e38654452ef32a00ceb369b4dfb003361bd0fc5a4eb1956c2" } } ], "extra": [ 1, 61, 20, 105, 243, 141, 64, 46, 167, 165, 11, 165, 212, 86, 249, 127, 39, 144, 99, 249, 11, 22, 174, 175, 68, 83, 110, 127, 197, 241, 54, 145, 209, 2, 17, 0, 0, 0, 3, 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