Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 534fce7a68e16a6b7ac93719e5ba9b2c55974f4480ab58e90146d9f56f9b0160

Tx prefix hash: a23e00af53dd8812cc0579a40a5ca5955698f74cab50cb57d9f3e6266aac59a2
Tx public key: 7d1b8e74f622bf0ffef2aa2c40bfc17aa503097554ffca72744f355774f657c5
Timestamp: 1675006680 Timestamp [UCT]: 2023-01-29 15:38:00 Age [y:d:h:m:s]: 02:073:13:57:20
Block: 685433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574202 RingCT/type: yes/0
Extra: 017d1b8e74f622bf0ffef2aa2c40bfc17aa503097554ffca72744f355774f657c5021100000011835e4d22000000000000000000

1 output(s) for total of 3.287576511000 dcy

stealth address amount amount idx
00: 58360150813e7aaff2f75c2afdf88c62eea2a94c5e9aba422969aaf5e626bd17 3.287576511000 1127756 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": 685443, "vin": [ { "gen": { "height": 685433 } } ], "vout": [ { "amount": 3287576511, "target": { "key": "58360150813e7aaff2f75c2afdf88c62eea2a94c5e9aba422969aaf5e626bd17" } } ], "extra": [ 1, 125, 27, 142, 116, 246, 34, 191, 15, 254, 242, 170, 44, 64, 191, 193, 122, 165, 3, 9, 117, 84, 255, 202, 114, 116, 79, 53, 87, 116, 246, 87, 197, 2, 17, 0, 0, 0, 17, 131, 94, 77, 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