Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ced2a7fb9589198c5a085acff6512a132ca261737ae4b3cfe6c9b1a096b2d0

Tx prefix hash: 83a15aed82c86128e1961957ba95c6158cbcff62dfba4bb0b15b1eb6771fcb3d
Tx public key: ca16b8728371b43f891615f07f596cd318996dd7089c66f3182e1ff1d2ba9485
Timestamp: 1729182630 Timestamp [UCT]: 2024-10-17 16:30:30 Age [y:d:h:m:s]: 00:082:06:01:16
Block: 1133687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58775 RingCT/type: yes/0
Extra: 01ca16b8728371b43f891615f07f596cd318996dd7089c66f3182e1ff1d2ba9485021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7acb1a9a9ae25707b7029c57d7c070db167f5710e7c935d887b31a395dc470db 0.600000000000 1616870 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": 1133697, "vin": [ { "gen": { "height": 1133687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7acb1a9a9ae25707b7029c57d7c070db167f5710e7c935d887b31a395dc470db" } } ], "extra": [ 1, 202, 22, 184, 114, 131, 113, 180, 63, 137, 22, 21, 240, 127, 89, 108, 211, 24, 153, 109, 215, 8, 156, 102, 243, 24, 46, 31, 241, 210, 186, 148, 133, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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