Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b4058a4f1b80705d60e204daf7d31bfd1bd3fd3fe19dfc5a3b1ab904ff3bf42

Tx prefix hash: af179858ee3a397d6c7ec28944771ff7794e21e2794346209f092b1624ac5e3c
Tx public key: 95b6f98969d9c2fbe575990adf56c48eb4b8393897f3c4383682c6e8ff49f3c5
Timestamp: 1726973674 Timestamp [UCT]: 2024-09-22 02:54:34 Age [y:d:h:m:s]: 00:067:08:20:26
Block: 1115369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48142 RingCT/type: yes/0
Extra: 0195b6f98969d9c2fbe575990adf56c48eb4b8393897f3c4383682c6e8ff49f3c502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57f6d9e85c3af7fbb608c0a9d3d2aaf62ce4d1c2cfa3a3da3af1d75cb3af22ea 0.600000000000 1595480 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": 1115379, "vin": [ { "gen": { "height": 1115369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57f6d9e85c3af7fbb608c0a9d3d2aaf62ce4d1c2cfa3a3da3af1d75cb3af22ea" } } ], "extra": [ 1, 149, 182, 249, 137, 105, 217, 194, 251, 229, 117, 153, 10, 223, 86, 196, 142, 180, 184, 57, 56, 151, 243, 196, 56, 54, 130, 198, 232, 255, 73, 243, 197, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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