Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4355f9e131ff7f5515bea517687af1f63f3062c50e02b4f882a868d26e6912b

Tx prefix hash: c9248d8e522d2f3185edccfc70b5a3b5358414fce38470583e15dc7f7b886e7a
Tx public key: c64754e9b991fb6a98d32cc9731d07f6620a84f1809d991b628a9d9dcef63c5a
Timestamp: 1699563348 Timestamp [UCT]: 2023-11-09 20:55:48 Age [y:d:h:m:s]: 01:151:05:22:50
Block: 888131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369260 RingCT/type: yes/0
Extra: 01c64754e9b991fb6a98d32cc9731d07f6620a84f1809d991b628a9d9dcef63c5a021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.700250322000 dcy

stealth address amount amount idx
00: 0c9aadd1f72ffe776ddfb03def8e115f141f735c8c91e41a0b1ccb222791641d 0.700250322000 1344054 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": 888141, "vin": [ { "gen": { "height": 888131 } } ], "vout": [ { "amount": 700250322, "target": { "key": "0c9aadd1f72ffe776ddfb03def8e115f141f735c8c91e41a0b1ccb222791641d" } } ], "extra": [ 1, 198, 71, 84, 233, 185, 145, 251, 106, 152, 211, 44, 201, 115, 29, 7, 246, 98, 10, 132, 241, 128, 157, 153, 27, 98, 138, 157, 157, 206, 246, 60, 90, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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