Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9072fbbf59bcaf4a753d9eba732a94a9556c376cf68843bb9feed688c9c41d66

Tx prefix hash: 2cc1326b9dba7b823b33e2420085986ec9d34b01e1d470b7be75e05aa437b56e
Tx public key: 94a6fab08e5f53d7511a3df8c7518cbacf36f366c24c86e0f1b5afbca193881e
Timestamp: 1729708234 Timestamp [UCT]: 2024-10-23 18:30:34 Age [y:d:h:m:s]: 00:141:12:14:40
Block: 1138006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100943 RingCT/type: yes/0
Extra: 0194a6fab08e5f53d7511a3df8c7518cbacf36f366c24c86e0f1b5afbca193881e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dcc154c346bb865af9467a5d54a2e51bbfdbce5c4b56733eb0eb2fe71936f08 0.600000000000 1621603 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": 1138016, "vin": [ { "gen": { "height": 1138006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dcc154c346bb865af9467a5d54a2e51bbfdbce5c4b56733eb0eb2fe71936f08" } } ], "extra": [ 1, 148, 166, 250, 176, 142, 95, 83, 215, 81, 26, 61, 248, 199, 81, 140, 186, 207, 54, 243, 102, 194, 76, 134, 224, 241, 181, 175, 188, 161, 147, 136, 30, 2, 17, 0, 0, 0, 2, 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