Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eba6b65ea60ce27c2cdc4d127347648067975513de936c69cc6e47618f673e03

Tx prefix hash: 68d5b614f0a3e39e0b2a775d43ac839ad6cfba73cebbc6e6e499d8b9ac9df56d
Tx public key: e61c276763346c9e34964a8a913941f20ce09fef9b2f5021e23e4aa664bec345
Timestamp: 1708013434 Timestamp [UCT]: 2024-02-15 16:10:34 Age [y:d:h:m:s]: 01:055:06:39:19
Block: 958173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300546 RingCT/type: yes/0
Extra: 01e61c276763346c9e34964a8a913941f20ce09fef9b2f5021e23e4aa664bec3450211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d40360602dc30d910172cd9cdf640039fe3a2ce5d4ca4d3c7fbe0f6bced59581 0.600000000000 1417528 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": 958183, "vin": [ { "gen": { "height": 958173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d40360602dc30d910172cd9cdf640039fe3a2ce5d4ca4d3c7fbe0f6bced59581" } } ], "extra": [ 1, 230, 28, 39, 103, 99, 52, 108, 158, 52, 150, 74, 138, 145, 57, 65, 242, 12, 224, 159, 239, 155, 47, 80, 33, 226, 62, 74, 166, 100, 190, 195, 69, 2, 17, 0, 0, 0, 1, 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