Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc98b9b6b776210bb77bcc329fe45ea8e98d07ac38c83ab4f36f9fc8bf17c3a

Tx prefix hash: 71d152544ebe3a424f1dd5829c33f826a61d8d0998c2e100cd3b445649fc0b8c
Tx public key: 5fcd0ae8d3909230fa0bb73f302fa3e7204ef955cf467a656f0f983f8832405a
Timestamp: 1703191178 Timestamp [UCT]: 2023-12-21 20:39:38 Age [y:d:h:m:s]: 01:039:05:56:16
Block: 918199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289147 RingCT/type: yes/0
Extra: 015fcd0ae8d3909230fa0bb73f302fa3e7204ef955cf467a656f0f983f8832405a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2523fed71b9363cbc043057dd7ea02aecca0c18d1ac91b61e445a973a5ff7994 0.600000000000 1375841 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": 918209, "vin": [ { "gen": { "height": 918199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2523fed71b9363cbc043057dd7ea02aecca0c18d1ac91b61e445a973a5ff7994" } } ], "extra": [ 1, 95, 205, 10, 232, 211, 144, 146, 48, 250, 11, 183, 63, 48, 47, 163, 231, 32, 78, 249, 85, 207, 70, 122, 101, 111, 15, 152, 63, 136, 50, 64, 90, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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