Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e0519cdb3eab984e8214f01b6b11c98a1b08e0521e369a28b36225b1a810d22

Tx prefix hash: a34dfb195c0363d35657a86de68dba8dcca025e6243fa822df7afba3a0a5eb9e
Tx public key: 305adca472deff3c512dd0df0adfafd5449671fd700c36e3aa59bdfd3febb053
Timestamp: 1702687881 Timestamp [UCT]: 2023-12-16 00:51:21 Age [y:d:h:m:s]: 01:180:09:31:06
Block: 914024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390058 RingCT/type: yes/0
Extra: 01305adca472deff3c512dd0df0adfafd5449671fd700c36e3aa59bdfd3febb05302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a19401990fef1f22c81a9cf9404503ca69419b04abc17a821d00bb49b6b60d4 0.600000000000 1371306 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": 914034, "vin": [ { "gen": { "height": 914024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a19401990fef1f22c81a9cf9404503ca69419b04abc17a821d00bb49b6b60d4" } } ], "extra": [ 1, 48, 90, 220, 164, 114, 222, 255, 60, 81, 45, 208, 223, 10, 223, 175, 213, 68, 150, 113, 253, 112, 12, 54, 227, 170, 89, 189, 253, 63, 235, 176, 83, 2, 17, 0, 0, 0, 2, 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