Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e81f56be8c8a665e970b3edd8e50d711297480f1cd2738b545e5c5c26ac023e8

Tx prefix hash: 67821cc18b0d6e3f3bd4d4217bdfc2fb06a524b65d0f1b1694327a6081143890
Tx public key: b678876cfceb29f0c161721aca47415b82a3e5f9c3bb98f552db268a9754d622
Timestamp: 1711049582 Timestamp [UCT]: 2024-03-21 19:33:02 Age [y:d:h:m:s]: 00:236:18:13:24
Block: 983371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169488 RingCT/type: yes/0
Extra: 01b678876cfceb29f0c161721aca47415b82a3e5f9c3bb98f552db268a9754d6220211000000100011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c79fec8eb19db359717ea1d59bc8960c7b8ade3eeaee3ab94df7ff43a0c73dc5 0.600000000000 1443498 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": 983381, "vin": [ { "gen": { "height": 983371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c79fec8eb19db359717ea1d59bc8960c7b8ade3eeaee3ab94df7ff43a0c73dc5" } } ], "extra": [ 1, 182, 120, 135, 108, 252, 235, 41, 240, 193, 97, 114, 26, 202, 71, 65, 91, 130, 163, 229, 249, 195, 187, 152, 245, 82, 219, 38, 138, 151, 84, 214, 34, 2, 17, 0, 0, 0, 16, 0, 17, 5, 91, 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