Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a24f64ebf5ae5c3ce9be9e3124ac7f81e2c1fda992bb2350186a991bf23f163

Tx prefix hash: 284d53692d816f5c86f21280aa29f20960d4cf161268f4069a0e2024e7875ef4
Tx public key: 17d7ed5c352c3d2dd7a35adf7d8fa4bfbbe44d1a76524aba5734185fe7643142
Timestamp: 1715215123 Timestamp [UCT]: 2024-05-09 00:38:43 Age [y:d:h:m:s]: 01:018:18:38:35
Block: 1017890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274355 RingCT/type: yes/0
Extra: 0117d7ed5c352c3d2dd7a35adf7d8fa4bfbbe44d1a76524aba5734185fe76431420211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5d4beb56c54ddb43c7d71aadd78426eef011b2b0c8a20b4b5d0ec69a34b4a65 0.600000000000 1481675 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": 1017900, "vin": [ { "gen": { "height": 1017890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5d4beb56c54ddb43c7d71aadd78426eef011b2b0c8a20b4b5d0ec69a34b4a65" } } ], "extra": [ 1, 23, 215, 237, 92, 53, 44, 61, 45, 215, 163, 90, 223, 125, 143, 164, 191, 187, 228, 77, 26, 118, 82, 74, 186, 87, 52, 24, 95, 231, 100, 49, 66, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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