Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf940720230fbd6652e1b53745402819c133a9448de86ebdf71cd785f62aa065

Tx prefix hash: 7bcd6ff30301867df00e51b0e9c042f00a24b76d75c6e4272487e3e275beb948
Tx public key: 2b4f132de6bf4a026f78f5b6c4aab167e590d7e444ebbb59b92a8c3c01be4d44
Timestamp: 1712665931 Timestamp [UCT]: 2024-04-09 12:32:11 Age [y:d:h:m:s]: 00:262:03:00:44
Block: 996731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187647 RingCT/type: yes/0
Extra: 012b4f132de6bf4a026f78f5b6c4aab167e590d7e444ebbb59b92a8c3c01be4d44021100000003bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87120067a9a472744dfeb2d95c3e03a8945436c34423ee08ce9ed6bea1c96825 0.600000000000 1457157 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": 996741, "vin": [ { "gen": { "height": 996731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87120067a9a472744dfeb2d95c3e03a8945436c34423ee08ce9ed6bea1c96825" } } ], "extra": [ 1, 43, 79, 19, 45, 230, 191, 74, 2, 111, 120, 245, 182, 196, 170, 177, 103, 229, 144, 215, 228, 68, 235, 187, 89, 185, 42, 140, 60, 1, 190, 77, 68, 2, 17, 0, 0, 0, 3, 191, 162, 34, 33, 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