Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d72c8dc6aaa94a47821d1c1a2f938255374ea9ffc7544627272642877e731be

Tx prefix hash: bd099d373b84993cd3cadb8e40341f4514764909262f2b7b6629a4b0a224cde3
Tx public key: 33948e7293078a6c62cf3a9ae2e7b712d6f97c3f65387b8379dd592e53b21f83
Timestamp: 1719948118 Timestamp [UCT]: 2024-07-02 19:21:58 Age [y:d:h:m:s]: 00:281:11:25:11
Block: 1057126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201123 RingCT/type: yes/0
Extra: 0133948e7293078a6c62cf3a9ae2e7b712d6f97c3f65387b8379dd592e53b21f8302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba3215dbd0304c9e690dd375c4d22daa35b4379c0282228beed9be8064d48456 0.600000000000 1527557 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": 1057136, "vin": [ { "gen": { "height": 1057126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba3215dbd0304c9e690dd375c4d22daa35b4379c0282228beed9be8064d48456" } } ], "extra": [ 1, 51, 148, 142, 114, 147, 7, 138, 108, 98, 207, 58, 154, 226, 231, 183, 18, 214, 249, 124, 63, 101, 56, 123, 131, 121, 221, 89, 46, 83, 178, 31, 131, 2, 17, 0, 0, 0, 2, 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