Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 477719ee9748ca99c09d6d6020137df0513db9fec0b12b7414cb3c635411b843

Tx prefix hash: e1ad8090127b91b1d7d4e150a58122ecf256f0e748b7ae441b973e81740f494c
Tx public key: 8ff05f7f4bf2df14b08a0d991e1f24958666b089081b1cf7af803fec535942a7
Timestamp: 1704956432 Timestamp [UCT]: 2024-01-11 07:00:32 Age [y:d:h:m:s]: 01:045:22:56:49
Block: 932818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293917 RingCT/type: yes/0
Extra: 018ff05f7f4bf2df14b08a0d991e1f24958666b089081b1cf7af803fec535942a702110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c5fa4d41b3e9d1bcfb2209531d45559e87856af55430e455873cb624efe72ec 0.600000000000 1390758 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": 932828, "vin": [ { "gen": { "height": 932818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c5fa4d41b3e9d1bcfb2209531d45559e87856af55430e455873cb624efe72ec" } } ], "extra": [ 1, 143, 240, 95, 127, 75, 242, 223, 20, 176, 138, 13, 153, 30, 31, 36, 149, 134, 102, 176, 137, 8, 27, 28, 247, 175, 128, 63, 236, 83, 89, 66, 167, 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