Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f51783ee2dc34989a6de7303e56b6235789d364ba01ce7333f41c60e47b8dfb

Tx prefix hash: 07796f172b6d703adb88f9d60648002fe7cad240e8604eee722d7b67beaea73b
Tx public key: 58843f48229690eb99aeb2406ae1752200b35cb51f8b5d3af7f873c42e8d12b8
Timestamp: 1711570222 Timestamp [UCT]: 2024-03-27 20:10:22 Age [y:d:h:m:s]: 01:013:08:00:38
Block: 987683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270491 RingCT/type: yes/0
Extra: 0158843f48229690eb99aeb2406ae1752200b35cb51f8b5d3af7f873c42e8d12b802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 239643f05b702e508dc96f10caa3c917194d055d1fc5dd724e2a3ccdf0a7f350 0.600000000000 1447938 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": 987693, "vin": [ { "gen": { "height": 987683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "239643f05b702e508dc96f10caa3c917194d055d1fc5dd724e2a3ccdf0a7f350" } } ], "extra": [ 1, 88, 132, 63, 72, 34, 150, 144, 235, 153, 174, 178, 64, 106, 225, 117, 34, 0, 179, 92, 181, 31, 139, 93, 58, 247, 248, 115, 196, 46, 141, 18, 184, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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