Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 004dd995ea2be1cfd064933fc0cb8d58e358824b70460cd77c0a73e920dfed3e

Tx prefix hash: c0a949711bc6d1d6a7319beea63e19d5f1c927e9725ea5f1e97f34e356f498c5
Tx public key: 2038c4b8117b0bd8c900d721684de2138a4c04616313ebd653d3733c536da748
Timestamp: 1706527031 Timestamp [UCT]: 2024-01-29 11:17:11 Age [y:d:h:m:s]: 01:079:17:48:12
Block: 945839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318080 RingCT/type: yes/0
Extra: 012038c4b8117b0bd8c900d721684de2138a4c04616313ebd653d3733c536da7480211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cb0140e4405c4c24f1d91f145af2373bf17f39c9d2676ad25fd46f8f91b606b 0.600000000000 1404163 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": 945849, "vin": [ { "gen": { "height": 945839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cb0140e4405c4c24f1d91f145af2373bf17f39c9d2676ad25fd46f8f91b606b" } } ], "extra": [ 1, 32, 56, 196, 184, 17, 123, 11, 216, 201, 0, 215, 33, 104, 77, 226, 19, 138, 76, 4, 97, 99, 19, 235, 214, 83, 211, 115, 60, 83, 109, 167, 72, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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