Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b11a3fa262e236197e06ac0281a54ff979b4de71e87d6f6d24c6b698608625c

Tx prefix hash: aee899192daa57b9d615e6b5fb43146152cd4b3622c4618b986a340db5bb8132
Tx public key: 8f3cb12880a8518244c7a61c6cb9669685db4204be13c10b7c3acd2217337853
Timestamp: 1707652624 Timestamp [UCT]: 2024-02-11 11:57:04 Age [y:d:h:m:s]: 00:315:00:13:49
Block: 955183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225552 RingCT/type: yes/0
Extra: 018f3cb12880a8518244c7a61c6cb9669685db4204be13c10b7c3acd221733785302110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 504c74ca5add650fded7ebfe308ae4f9492ab3c6bf9dd29b3c8c715d92d7a4c3 0.600000000000 1414469 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": 955193, "vin": [ { "gen": { "height": 955183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "504c74ca5add650fded7ebfe308ae4f9492ab3c6bf9dd29b3c8c715d92d7a4c3" } } ], "extra": [ 1, 143, 60, 177, 40, 128, 168, 81, 130, 68, 199, 166, 28, 108, 185, 102, 150, 133, 219, 66, 4, 190, 19, 193, 11, 124, 58, 205, 34, 23, 51, 120, 83, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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