Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed412c6ef4c9978cfeb4fbf1e483a55bf5b0c8008ff60490c59f1095569408d4

Tx prefix hash: 5042bb9acab9011877f65c04183b78172657b821dbfba98da487b219d25c9f12
Tx public key: 0e0e054c8fc75d47b32271ea597a86e6614c4b2187f5ddf44547b476d69ae161
Timestamp: 1730040300 Timestamp [UCT]: 2024-10-27 14:45:00 Age [y:d:h:m:s]: 00:233:11:33:17
Block: 1140760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166595 RingCT/type: yes/0
Extra: 010e0e054c8fc75d47b32271ea597a86e6614c4b2187f5ddf44547b476d69ae161021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384b0b96f5ef7c5a1e085f7fa253fde70d12d435100d5be582f06915b34ab7e0 0.600000000000 1624563 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": 1140770, "vin": [ { "gen": { "height": 1140760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384b0b96f5ef7c5a1e085f7fa253fde70d12d435100d5be582f06915b34ab7e0" } } ], "extra": [ 1, 14, 14, 5, 76, 143, 199, 93, 71, 179, 34, 113, 234, 89, 122, 134, 230, 97, 76, 75, 33, 135, 245, 221, 244, 69, 71, 180, 118, 214, 154, 225, 97, 2, 17, 0, 0, 0, 1, 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