Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e68aeb33359275a568e009cbb2dcc4e5fedee8bcde16ac05d62e873692d18ec

Tx prefix hash: a540010883f8456335cd6efed6411117cec9f273ad3d27c7912e9c087022dbe0
Tx public key: 4a8aeb552cbb922f0d2104fafd5ba3a7e844f2f1e7389f2b26cbeef6c61772be
Timestamp: 1733602162 Timestamp [UCT]: 2024-12-07 20:09:22 Age [y:d:h:m:s]: 00:335:00:21:26
Block: 1170225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236945 RingCT/type: yes/0
Extra: 014a8aeb552cbb922f0d2104fafd5ba3a7e844f2f1e7389f2b26cbeef6c61772be0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fe84a59d70fe7f1cc0ac272dc589cad8ef7001805acecd8ba77e8450bc64e52 0.600000000000 1655954 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": 1170235, "vin": [ { "gen": { "height": 1170225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fe84a59d70fe7f1cc0ac272dc589cad8ef7001805acecd8ba77e8450bc64e52" } } ], "extra": [ 1, 74, 138, 235, 85, 44, 187, 146, 47, 13, 33, 4, 250, 253, 91, 163, 167, 232, 68, 242, 241, 231, 56, 159, 43, 38, 203, 238, 246, 198, 23, 114, 190, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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