Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf20543a1a8c18aa57a19217e74e6b5c60096603f638f0a62f0caa74b8ee8ed1

Tx prefix hash: a7572a0b59b17dd11fdcc0f53eb2f5a0f2220ce53c51c69e3372c86688546670
Tx public key: 93c4c44705dfa1a784bf10affa0fb65c6b7cbdab0443960c28f248524c6d55a9
Timestamp: 1731265235 Timestamp [UCT]: 2024-11-10 19:00:35 Age [y:d:h:m:s]: 00:131:02:50:08
Block: 1150863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93527 RingCT/type: yes/0
Extra: 0193c4c44705dfa1a784bf10affa0fb65c6b7cbdab0443960c28f248524c6d55a90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14abd4d23249cf0c45543d9f4658db6e880cdec970e14dca2962d1e45eaade6e 0.600000000000 1636284 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": 1150873, "vin": [ { "gen": { "height": 1150863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14abd4d23249cf0c45543d9f4658db6e880cdec970e14dca2962d1e45eaade6e" } } ], "extra": [ 1, 147, 196, 196, 71, 5, 223, 161, 167, 132, 191, 16, 175, 250, 15, 182, 92, 107, 124, 189, 171, 4, 67, 150, 12, 40, 242, 72, 82, 76, 109, 85, 169, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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