Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967e386d2795062974de772b280f776bb4c68c202c83a0a0f248edbcfdae19a5

Tx prefix hash: 15e112e16161e842926d47f203eb78f5b574ea78a1fe738a900d183adec1e54d
Tx public key: 4621f0168e9065ba512f097b014c3a5a204ab77d4aa5ba3f427cb811bbe44244
Timestamp: 1617593612 Timestamp [UCT]: 2021-04-05 03:33:32 Age [y:d:h:m:s]: 04:039:05:57:52
Block: 233461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1048474 RingCT/type: yes/0
Extra: 014621f0168e9065ba512f097b014c3a5a204ab77d4aa5ba3f427cb811bbe442440211000000180dc70aa7000000000000000000

1 output(s) for total of 103.382580739000 dcy

stealth address amount amount idx
00: edb7e2b8e6a885acc3724fe27de69c22c05173781485523758ba8210d4fe9249 103.382580739000 484827 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": 233471, "vin": [ { "gen": { "height": 233461 } } ], "vout": [ { "amount": 103382580739, "target": { "key": "edb7e2b8e6a885acc3724fe27de69c22c05173781485523758ba8210d4fe9249" } } ], "extra": [ 1, 70, 33, 240, 22, 142, 144, 101, 186, 81, 47, 9, 123, 1, 76, 58, 90, 32, 74, 183, 125, 74, 165, 186, 63, 66, 124, 184, 17, 187, 228, 66, 68, 2, 17, 0, 0, 0, 24, 13, 199, 10, 167, 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