Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a295ca94140c0dd0c8014e4d0efa3573498e500cad360ed8bbb814d4fb4de77

Tx prefix hash: 5b1cabb057828dcc5dd4dad62b2cb365717eb597c9a4df57e50c666154c82c63
Tx public key: 1fe6e077e989fb8a83aad16f08b1b144d9be11a75371fd17352af43c5b228cd7
Timestamp: 1698718672 Timestamp [UCT]: 2023-10-31 02:17:52 Age [y:d:h:m:s]: 02:006:16:35:47
Block: 881328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524353 RingCT/type: yes/0
Extra: 011fe6e077e989fb8a83aad16f08b1b144d9be11a75371fd17352af43c5b228cd702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.737555133000 dcy

stealth address amount amount idx
00: c5c74767f94ad14f8f567078d3c52d52fdf998facff8b877ef8e36db4ca27705 0.737555133000 1336908 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": 881338, "vin": [ { "gen": { "height": 881328 } } ], "vout": [ { "amount": 737555133, "target": { "key": "c5c74767f94ad14f8f567078d3c52d52fdf998facff8b877ef8e36db4ca27705" } } ], "extra": [ 1, 31, 230, 224, 119, 233, 137, 251, 138, 131, 170, 209, 111, 8, 177, 177, 68, 217, 190, 17, 167, 83, 113, 253, 23, 53, 42, 244, 60, 91, 34, 140, 215, 2, 17, 0, 0, 0, 4, 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