Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b625a01664a053f087515243bbd8b93350f5b9bb2fb83d978ed2974c7ce4ccca

Tx prefix hash: 863df5b14bb807440a7a42b6d9e99d4c33a53bf7f0bb119cf5f96075404d76d6
Tx public key: 4cc3a60e9f4178c20ae47d0113db6e53423efa0a9f10601f3d925fb75e511146
Timestamp: 1705234652 Timestamp [UCT]: 2024-01-14 12:17:32 Age [y:d:h:m:s]: 01:085:23:33:28
Block: 935136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322552 RingCT/type: yes/0
Extra: 014cc3a60e9f4178c20ae47d0113db6e53423efa0a9f10601f3d925fb75e51114602110000000641ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9137e91d984914f4d49f5f2a7dc7ca3ca0b6b24df62c5510516fab61586306c1 0.600000000000 1393152 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": 935146, "vin": [ { "gen": { "height": 935136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9137e91d984914f4d49f5f2a7dc7ca3ca0b6b24df62c5510516fab61586306c1" } } ], "extra": [ 1, 76, 195, 166, 14, 159, 65, 120, 194, 10, 228, 125, 1, 19, 219, 110, 83, 66, 62, 250, 10, 159, 16, 96, 31, 61, 146, 95, 183, 94, 81, 17, 70, 2, 17, 0, 0, 0, 6, 65, 238, 28, 155, 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