Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b187f094e75d96e5097182e07dccc6d5f9ca615b1ee3b6225d6776959e520a03

Tx prefix hash: 3b353e9f731a6ae8af5a9aaa58ed5ae91f5b1738973841b7ded76a209d700a18
Tx public key: 2b71ce281d6af25773b69cbd6edae86b10ec83bc6a24e7a00144e41ecf28191d
Timestamp: 1735904498 Timestamp [UCT]: 2025-01-03 11:41:38 Age [y:d:h:m:s]: 00:166:14:46:11
Block: 1189308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118745 RingCT/type: yes/0
Extra: 012b71ce281d6af25773b69cbd6edae86b10ec83bc6a24e7a00144e41ecf28191d02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b854192355b2631e8e4286ab3eeb1e121a0df7cd26efd955a0095c3d23b344a 0.600000000000 1675815 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": 1189318, "vin": [ { "gen": { "height": 1189308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b854192355b2631e8e4286ab3eeb1e121a0df7cd26efd955a0095c3d23b344a" } } ], "extra": [ 1, 43, 113, 206, 40, 29, 106, 242, 87, 115, 182, 156, 189, 110, 218, 232, 107, 16, 236, 131, 188, 106, 36, 231, 160, 1, 68, 228, 30, 207, 40, 25, 29, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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