Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a871f958891cf0ada2c494d24a8fbef3e9e8633a96319b8d816b4b0b15191c7a

Tx prefix hash: 8bec4054519892022a4e5efceedb37fa17a1eea68642a40e050c7215827b6ecd
Tx public key: 1e64442cfa49908508dd82536b6c56a3dfa39a34457fc42b2a0d0aad4aafe1a1
Timestamp: 1735831525 Timestamp [UCT]: 2025-01-02 15:25:25 Age [y:d:h:m:s]: 00:348:12:31:14
Block: 1188672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246636 RingCT/type: yes/0
Extra: 011e64442cfa49908508dd82536b6c56a3dfa39a34457fc42b2a0d0aad4aafe1a10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec2dbb4acc5dee44b0fef42968c5497f287e120edf4be1b21b81a443151d76f5 0.600000000000 1675175 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": 1188682, "vin": [ { "gen": { "height": 1188672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec2dbb4acc5dee44b0fef42968c5497f287e120edf4be1b21b81a443151d76f5" } } ], "extra": [ 1, 30, 100, 68, 44, 250, 73, 144, 133, 8, 221, 130, 83, 107, 108, 86, 163, 223, 163, 154, 52, 69, 127, 196, 43, 42, 13, 10, 173, 74, 175, 225, 161, 2, 17, 0, 0, 0, 3, 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