Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b986c6e3ea13647a35f090e4291a382d4ce7919b97c3200990337d946c34926c

Tx prefix hash: 5e9fdf2a24d9ed801a72dd2d5d3b6aff80f9e8228d9b107307e8fc0b7752a6b0
Tx public key: ac214d3bf2c6e3598f3dcde266d6759c0b51573c878a082a59ca5b16bb14c126
Timestamp: 1698360162 Timestamp [UCT]: 2023-10-26 22:42:42 Age [y:d:h:m:s]: 02:027:16:32:25
Block: 878374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539373 RingCT/type: yes/0
Extra: 01ac214d3bf2c6e3598f3dcde266d6759c0b51573c878a082a59ca5b16bb14c1260211000000034b8f5122000000000000000000

1 output(s) for total of 0.754366376000 dcy

stealth address amount amount idx
00: 835051e886345eaf73b036f5ea6c96d149bbb4a026c8d460f0a103b8bb9519b6 0.754366376000 1333812 of 0

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": 878384, "vin": [ { "gen": { "height": 878374 } } ], "vout": [ { "amount": 754366376, "target": { "key": "835051e886345eaf73b036f5ea6c96d149bbb4a026c8d460f0a103b8bb9519b6" } } ], "extra": [ 1, 172, 33, 77, 59, 242, 198, 227, 89, 143, 61, 205, 226, 102, 214, 117, 156, 11, 81, 87, 60, 135, 138, 8, 42, 89, 202, 91, 22, 187, 20, 193, 38, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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