Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bca3ce5548e5bd171e10d89c8f0625cce114a7d0f2d2e7e16f1ca3742f99a010

Tx prefix hash: 5ca5504fd59405c3af315461a4a68b4b3407ab02ff2a4745153b05ac769c0323
Tx public key: 88846d0fcf213ea34c6b8c819bc3a6d6466d9d3d30912d417cc3988046786105
Timestamp: 1732812317 Timestamp [UCT]: 2024-11-28 16:45:17 Age [y:d:h:m:s]: 00:125:09:18:35
Block: 1163679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89413 RingCT/type: yes/0
Extra: 0188846d0fcf213ea34c6b8c819bc3a6d6466d9d3d30912d417cc39880467861050211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 623419c7622e23eb48bfa819de458de1d83af25861e469c3e87e46a53debdeb4 0.600000000000 1649346 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": 1163689, "vin": [ { "gen": { "height": 1163679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "623419c7622e23eb48bfa819de458de1d83af25861e469c3e87e46a53debdeb4" } } ], "extra": [ 1, 136, 132, 109, 15, 207, 33, 62, 163, 76, 107, 140, 129, 155, 195, 166, 214, 70, 109, 157, 61, 48, 145, 45, 65, 124, 195, 152, 128, 70, 120, 97, 5, 2, 17, 0, 0, 0, 6, 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