Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 883e0ee255df4028081efc49cd5da2c96d29f8916dcc5c2478761acca97f43d4

Tx prefix hash: 2c54b8871479db54e1ffd20c1659b7b057bb29f246b34561e4c74dd8f32f9bb3
Tx public key: 5ea758b0784523d5655ad8380cbefd0b8bece37b082cb94f26e5f568ef6cce84
Timestamp: 1737075693 Timestamp [UCT]: 2025-01-17 01:01:33 Age [y:d:h:m:s]: 00:059:11:31:56
Block: 1198971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42300 RingCT/type: yes/0
Extra: 015ea758b0784523d5655ad8380cbefd0b8bece37b082cb94f26e5f568ef6cce840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4af16991ef814dbb976dc7eabeedfaea6ff909a8f8a0f4832bca51387aadeabe 0.600000000000 1685598 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": 1198981, "vin": [ { "gen": { "height": 1198971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4af16991ef814dbb976dc7eabeedfaea6ff909a8f8a0f4832bca51387aadeabe" } } ], "extra": [ 1, 94, 167, 88, 176, 120, 69, 35, 213, 101, 90, 216, 56, 12, 190, 253, 11, 139, 236, 227, 123, 8, 44, 185, 79, 38, 229, 245, 104, 239, 108, 206, 132, 2, 17, 0, 0, 0, 2, 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