Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442e51e4474f6fdc16be06730a09e2a3ca28c3046a76d8dd472a6be6c6f49933

Tx prefix hash: 4c6b95082fee73fc5f2af7d49259793ef94cdf6bd46e6149c0e66755b8e86525
Tx public key: 9d74bf0797b4eeca50b0efa3c6f780095498b71e470bf201d80cd5bb4447529f
Timestamp: 1722120216 Timestamp [UCT]: 2024-07-27 22:43:36 Age [y:d:h:m:s]: 00:089:18:34:53
Block: 1075134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64269 RingCT/type: yes/0
Extra: 019d74bf0797b4eeca50b0efa3c6f780095498b71e470bf201d80cd5bb4447529f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69da6c2f1be431e20db15e139217a9decfd3b3bd46113423db354c988bbcb6d5 0.600000000000 1547657 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": 1075144, "vin": [ { "gen": { "height": 1075134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69da6c2f1be431e20db15e139217a9decfd3b3bd46113423db354c988bbcb6d5" } } ], "extra": [ 1, 157, 116, 191, 7, 151, 180, 238, 202, 80, 176, 239, 163, 198, 247, 128, 9, 84, 152, 183, 30, 71, 11, 242, 1, 216, 12, 213, 187, 68, 71, 82, 159, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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