Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 321d3391db99cc86ece329bfabd8ef34a31133063c0d3b354d33869ec1102695

Tx prefix hash: 0bba8e78d8da916a05176801041e6496170171e431e633624750706f9a9cd92f
Tx public key: 8ac3e30dfdccd1b6fdbbf1c60e5084c4046fefdd015b05f7726a3fb43c2a9e65
Timestamp: 1695751721 Timestamp [UCT]: 2023-09-26 18:08:41 Age [y:d:h:m:s]: 01:150:22:55:14
Block: 856722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368913 RingCT/type: yes/0
Extra: 018ac3e30dfdccd1b6fdbbf1c60e5084c4046fefdd015b05f7726a3fb43c2a9e650211000000074b8f5122000000000000000000

1 output(s) for total of 0.889865600000 dcy

stealth address amount amount idx
00: 6274c74bf1eabafba9e0be5aae889ebf3f102e9f4fbd40a0d4f6dea8e3e530b5 0.889865600000 1310808 of 0

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": 856732, "vin": [ { "gen": { "height": 856722 } } ], "vout": [ { "amount": 889865600, "target": { "key": "6274c74bf1eabafba9e0be5aae889ebf3f102e9f4fbd40a0d4f6dea8e3e530b5" } } ], "extra": [ 1, 138, 195, 227, 13, 253, 204, 209, 182, 253, 187, 241, 198, 14, 80, 132, 196, 4, 111, 239, 221, 1, 91, 5, 247, 114, 106, 63, 180, 60, 42, 158, 101, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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