Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e223a8f10952f99fbd83c942d1feada813427ec699a943a8e20144505e05939

Tx prefix hash: 9bf3c43435e7ed13c30a92c6d44055f65c22ded60d89ec8bde49ca9095659fb7
Tx public key: ba0851da9a9a3614eee410cefc315ff20eacbceb879b9bfd2b6d2373e7a889f5
Timestamp: 1710543096 Timestamp [UCT]: 2024-03-15 22:51:36 Age [y:d:h:m:s]: 01:010:04:11:35
Block: 979171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268222 RingCT/type: yes/0
Extra: 01ba0851da9a9a3614eee410cefc315ff20eacbceb879b9bfd2b6d2373e7a889f50211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3f8cc0f66597751f1c7bdef7c168976e69b0c933674a33cbe391ad072d79288 0.600000000000 1439204 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": 979181, "vin": [ { "gen": { "height": 979171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3f8cc0f66597751f1c7bdef7c168976e69b0c933674a33cbe391ad072d79288" } } ], "extra": [ 1, 186, 8, 81, 218, 154, 154, 54, 20, 238, 228, 16, 206, 252, 49, 95, 242, 14, 172, 188, 235, 135, 155, 155, 253, 43, 109, 35, 115, 231, 168, 137, 245, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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