Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f54a78873f2c3f2a3bd083e38ca836bb631d830c2d198ed228d563bd397b5b07

Tx prefix hash: e7b360181f4d6b9380ca9025c79e1dbdb53ced870ffe3ee61f455c4f6ae06e95
Tx public key: 36ed337e52ad9da2409a0229db72d85c9e06f083a6d8268f70349b40265c41f7
Timestamp: 1712846449 Timestamp [UCT]: 2024-04-11 14:40:49 Age [y:d:h:m:s]: 01:256:03:16:55
Block: 998227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441808 RingCT/type: yes/0
Extra: 0136ed337e52ad9da2409a0229db72d85c9e06f083a6d8268f70349b40265c41f702110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb2415b4f77bf0f0d2fa4e21909e8597228e44f76e776e6a9dfb07c7f2527378 0.600000000000 1458673 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": 998237, "vin": [ { "gen": { "height": 998227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb2415b4f77bf0f0d2fa4e21909e8597228e44f76e776e6a9dfb07c7f2527378" } } ], "extra": [ 1, 54, 237, 51, 126, 82, 173, 157, 162, 64, 154, 2, 41, 219, 114, 216, 92, 158, 6, 240, 131, 166, 216, 38, 143, 112, 52, 155, 64, 38, 92, 65, 247, 2, 17, 0, 0, 0, 10, 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