Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4080a1e3bb5dc1d8d15c8d7a4ae84b848cb1703de11e2bbc5f3567c37b31151c

Tx prefix hash: 0b7de705e329d378406c8bc2e472900f0b7b7699f01483824ad9020c2889ed51
Tx public key: bc1ad9cb2d14cf50e68067eea3177c06f1cc1c14170aa5d77b78cb5ee89cc724
Timestamp: 1695982950 Timestamp [UCT]: 2023-09-29 10:22:30 Age [y:d:h:m:s]: 01:192:02:13:12
Block: 858646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398332 RingCT/type: yes/0
Extra: 01bc1ad9cb2d14cf50e68067eea3177c06f1cc1c14170aa5d77b78cb5ee89cc72402110000000f4b8f5122000000000000000000

1 output(s) for total of 0.876898657000 dcy

stealth address amount amount idx
00: a470d6f907291efdc4f971cdf0678e950da27e1f9a2ac19c6f3209981572d395 0.876898657000 1312830 of 0

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": 858656, "vin": [ { "gen": { "height": 858646 } } ], "vout": [ { "amount": 876898657, "target": { "key": "a470d6f907291efdc4f971cdf0678e950da27e1f9a2ac19c6f3209981572d395" } } ], "extra": [ 1, 188, 26, 217, 203, 45, 20, 207, 80, 230, 128, 103, 238, 163, 23, 124, 6, 241, 204, 28, 20, 23, 10, 165, 215, 123, 120, 203, 94, 232, 156, 199, 36, 2, 17, 0, 0, 0, 15, 75, 143, 81, 34, 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