Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22aa89697f6482623bfd9fc6d449526222973075378317ccd82a8600fa6da4cb

Tx prefix hash: b585a746f3dba480271b47760077dc91c46f96e5cb8d5e00c65f0a13d14ce9f5
Tx public key: 9115f34aa616ec21303f146c8fc2f8aeea784e925604d562a2f38c5255675cc1
Timestamp: 1738193727 Timestamp [UCT]: 2025-01-29 23:35:27 Age [y:d:h:m:s]: 00:139:13:01:20
Block: 1207971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99687 RingCT/type: yes/0
Extra: 019115f34aa616ec21303f146c8fc2f8aeea784e925604d562a2f38c5255675cc1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9cedc2f86f2f9da0ae73cfeb99336f6ad654cf7c46695ff23f7a5c7ec84b8b7 0.600000000000 1694698 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": 1207981, "vin": [ { "gen": { "height": 1207971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9cedc2f86f2f9da0ae73cfeb99336f6ad654cf7c46695ff23f7a5c7ec84b8b7" } } ], "extra": [ 1, 145, 21, 243, 74, 166, 22, 236, 33, 48, 63, 20, 108, 143, 194, 248, 174, 234, 120, 78, 146, 86, 4, 213, 98, 162, 243, 140, 82, 85, 103, 92, 193, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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