Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7dba5b81733adcfafc7af08b0e954514d671d35cc1e9a0eb9fce3c2dadc70c

Tx prefix hash: 84b7d9f4f3da6def31dfbb807e84767fcbfd6751ffd0f6409c37ea02459c2a28
Tx public key: 8a0679b775c833f4d8d0fa411e52b8f0782d00fbeaf67071483330517bcceb38
Timestamp: 1726249222 Timestamp [UCT]: 2024-09-13 17:40:22 Age [y:d:h:m:s]: 00:163:05:02:26
Block: 1109361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116445 RingCT/type: yes/0
Extra: 018a0679b775c833f4d8d0fa411e52b8f0782d00fbeaf67071483330517bcceb38021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78b2175bf7999a5913447a7d0c218b805dbf2ea471c201335b0bf8909a835678 0.600000000000 1587586 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": 1109371, "vin": [ { "gen": { "height": 1109361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78b2175bf7999a5913447a7d0c218b805dbf2ea471c201335b0bf8909a835678" } } ], "extra": [ 1, 138, 6, 121, 183, 117, 200, 51, 244, 216, 208, 250, 65, 30, 82, 184, 240, 120, 45, 0, 251, 234, 246, 112, 113, 72, 51, 48, 81, 123, 204, 235, 56, 2, 17, 0, 0, 0, 3, 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