Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c464c315707362c2b34b4e4484b5a9dca771f2f78ac7a09bfd37c6551b3533d3

Tx prefix hash: 3df1f14d5c42853232860c3b8416db33b04f441162580061e173caacba9f4c1e
Tx public key: 3fefe6c7edd6b4f9b2f25596984a48f4cd08b69494a25116880696339b74c9c6
Timestamp: 1580486440 Timestamp [UCT]: 2020-01-31 16:00:40 Age [y:d:h:m:s]: 05:085:18:34:13
Block: 55984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213111 RingCT/type: yes/0
Extra: 013fefe6c7edd6b4f9b2f25596984a48f4cd08b69494a25116880696339b74c9c6021100000004dcee4b4d000000000000000000

1 output(s) for total of 400.407858217000 dcy

stealth address amount amount idx
00: 24d05838a0a0321d761a495656db47fba33ca4700556ed9946052f956f218d9b 400.407858217000 103253 of 0

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": 55994, "vin": [ { "gen": { "height": 55984 } } ], "vout": [ { "amount": 400407858217, "target": { "key": "24d05838a0a0321d761a495656db47fba33ca4700556ed9946052f956f218d9b" } } ], "extra": [ 1, 63, 239, 230, 199, 237, 214, 180, 249, 178, 242, 85, 150, 152, 74, 72, 244, 205, 8, 182, 148, 148, 162, 81, 22, 136, 6, 150, 51, 155, 116, 201, 198, 2, 17, 0, 0, 0, 4, 220, 238, 75, 77, 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