Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eab6f9aa50a951d0b8b6bb94bcb3039d59752160384e2355fde5c44b93fe8b9c

Tx prefix hash: 255d1aa1246b6cb0faf348b8fdc3a089a8fb5b3c582416f5a49db030606835a8
Tx public key: 159a692588236be8b1385039c107d95c58c45c06f316fa1697c1d46091f7b928
Timestamp: 1734512623 Timestamp [UCT]: 2024-12-18 09:03:43 Age [y:d:h:m:s]: 00:096:09:31:11
Block: 1177789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68644 RingCT/type: yes/0
Extra: 01159a692588236be8b1385039c107d95c58c45c06f316fa1697c1d46091f7b928021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95ad082cb640bd84d1cc9dcf106d4c994d7ce0105113d3327fa8fd47ee765d93 0.600000000000 1664166 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": 1177799, "vin": [ { "gen": { "height": 1177789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95ad082cb640bd84d1cc9dcf106d4c994d7ce0105113d3327fa8fd47ee765d93" } } ], "extra": [ 1, 21, 154, 105, 37, 136, 35, 107, 232, 177, 56, 80, 57, 193, 7, 217, 92, 88, 196, 92, 6, 243, 22, 250, 22, 151, 193, 212, 96, 145, 247, 185, 40, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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