Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9645923936b2e3136ddc0fd26b2941c4496423ae721b346714e8fb2fd89c6763

Tx prefix hash: 7e2bc79bb82e3b2d42dcd7608e00f5a440a20221dc629241f535f9f695ae296c
Tx public key: 51d62960f3b7c67c5147ffe5bc08c24584171f3653606c0ad7964d3160c1bb5e
Timestamp: 1714560288 Timestamp [UCT]: 2024-05-01 10:44:48 Age [y:d:h:m:s]: 00:319:16:03:53
Block: 1012459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228515 RingCT/type: yes/0
Extra: 0151d62960f3b7c67c5147ffe5bc08c24584171f3653606c0ad7964d3160c1bb5e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ca7747a8930875fb362b8f6eabb4863bdad256f076f3c5d7dca0ff801a706e 0.600000000000 1474997 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": 1012469, "vin": [ { "gen": { "height": 1012459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ca7747a8930875fb362b8f6eabb4863bdad256f076f3c5d7dca0ff801a706e" } } ], "extra": [ 1, 81, 214, 41, 96, 243, 183, 198, 124, 81, 71, 255, 229, 188, 8, 194, 69, 132, 23, 31, 54, 83, 96, 108, 10, 215, 150, 77, 49, 96, 193, 187, 94, 2, 17, 0, 0, 0, 1, 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