Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d2043a8726037711db5037794116666e5bb8dab76da5db87a61cf9cc291325

Tx prefix hash: 0c9a6ccc1122926cde6f41f7e16624f298098fec9e4eff53d4aeafa0a073343f
Tx public key: df876b5538f050ccc2f34b27f6c51bb7d418e9af13dc11f3883f2e2226cc23d3
Timestamp: 1713295341 Timestamp [UCT]: 2024-04-16 19:22:21 Age [y:d:h:m:s]: 00:355:23:46:11
Block: 1001954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254504 RingCT/type: yes/0
Extra: 01df876b5538f050ccc2f34b27f6c51bb7d418e9af13dc11f3883f2e2226cc23d30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6343c2bf4cd5f671db1bb98eabedf0f8e36a122b826f8810f5c14816f66bed38 0.600000000000 1462468 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": 1001964, "vin": [ { "gen": { "height": 1001954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6343c2bf4cd5f671db1bb98eabedf0f8e36a122b826f8810f5c14816f66bed38" } } ], "extra": [ 1, 223, 135, 107, 85, 56, 240, 80, 204, 194, 243, 75, 39, 246, 197, 27, 183, 212, 24, 233, 175, 19, 220, 17, 243, 136, 63, 46, 34, 38, 204, 35, 211, 2, 17, 0, 0, 0, 2, 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