Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e829931ce6ae24f7d48bb4ececc6da5815322d2246874cc680da766dea45f2b

Tx prefix hash: a7f5112cb19a53948a44ef72dc15a03c8b8e4b0419db9f523713a8a5fec29824
Tx public key: 9142b5813941336a2b6d40e6f452160c626b4d806ad1a4649f4c2339ec140b88
Timestamp: 1702307949 Timestamp [UCT]: 2023-12-11 15:19:09 Age [y:d:h:m:s]: 01:335:01:24:33
Block: 910882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498321 RingCT/type: yes/0
Extra: 019142b5813941336a2b6d40e6f452160c626b4d806ad1a4649f4c2339ec140b8802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4bf33024aa3043a73991f0a2b97b00cb59c9f0301ed6adc71f2af19bb521783 0.600000000000 1368057 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": 910892, "vin": [ { "gen": { "height": 910882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4bf33024aa3043a73991f0a2b97b00cb59c9f0301ed6adc71f2af19bb521783" } } ], "extra": [ 1, 145, 66, 181, 129, 57, 65, 51, 106, 43, 109, 64, 230, 244, 82, 22, 12, 98, 107, 77, 128, 106, 209, 164, 100, 159, 76, 35, 57, 236, 20, 11, 136, 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