Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de92925b084c082ccb9f8e0e0f25e9ec0c6a875da7d50aee06616b8581d719cb

Tx prefix hash: 3eea6e155659a08a41cb34720762b575c81990e066f56d0dc588fc9b62181b6c
Tx public key: bf34bb97916ce09b4485a7b72af18825a6ae7ef6dc0b3f1e3727a87cc0936147
Timestamp: 1700183202 Timestamp [UCT]: 2023-11-17 01:06:42 Age [y:d:h:m:s]: 01:213:11:23:48
Block: 893263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413692 RingCT/type: yes/0
Extra: 01bf34bb97916ce09b4485a7b72af18825a6ae7ef6dc0b3f1e3727a87cc093614702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.673362402000 dcy

stealth address amount amount idx
00: 709d979ae570fd67de47157aa1fa4fb26ba3e81b7741cb4ab2c966f36a0b6275 0.673362402000 1349426 of 0

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": 893273, "vin": [ { "gen": { "height": 893263 } } ], "vout": [ { "amount": 673362402, "target": { "key": "709d979ae570fd67de47157aa1fa4fb26ba3e81b7741cb4ab2c966f36a0b6275" } } ], "extra": [ 1, 191, 52, 187, 151, 145, 108, 224, 155, 68, 133, 167, 183, 42, 241, 136, 37, 166, 174, 126, 246, 220, 11, 63, 30, 55, 39, 168, 124, 192, 147, 97, 71, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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