Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 818924e847a6acf0376ee5e153fbf7ba24d0c5c074de259b6c553728852a6850

Tx prefix hash: 945bf8f616539d11727a71424598cd7d2e88247b533c21e5fb0c8c0c1f18ed92
Tx public key: 0100abc824636b0e96d015f69075680bd1c88e8b22040051203b367ba0041b8c
Timestamp: 1709518291 Timestamp [UCT]: 2024-03-04 02:11:31 Age [y:d:h:m:s]: 01:098:06:09:50
Block: 970665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331276 RingCT/type: yes/0
Extra: 010100abc824636b0e96d015f69075680bd1c88e8b22040051203b367ba0041b8c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf9d3638eb8012c1f5dcc4ff69dc6241cb95e597d6a82e4d1cfe3dde1f233ce3 0.600000000000 1430524 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": 970675, "vin": [ { "gen": { "height": 970665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf9d3638eb8012c1f5dcc4ff69dc6241cb95e597d6a82e4d1cfe3dde1f233ce3" } } ], "extra": [ 1, 1, 0, 171, 200, 36, 99, 107, 14, 150, 208, 21, 246, 144, 117, 104, 11, 209, 200, 142, 139, 34, 4, 0, 81, 32, 59, 54, 123, 160, 4, 27, 140, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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