Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6530791e5d27ac79b35314c5ebbe45b91f2b950187479e5a218ce68ff50f63b7

Tx prefix hash: b0ae6a65f4f16ef3abc60d960f237a817dea1e832149df793246cc52232bcba7
Tx public key: 7e474e9793eea6d734171b4cb32acd1979193bff9f7a73e97a55fcceb7820db3
Timestamp: 1720299710 Timestamp [UCT]: 2024-07-06 21:01:50 Age [y:d:h:m:s]: 00:342:21:54:59
Block: 1060033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244986 RingCT/type: yes/0
Extra: 017e474e9793eea6d734171b4cb32acd1979193bff9f7a73e97a55fcceb7820db302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db9bca1f31c9bdf3768c2993c1a8e3f5cba7e0ea85e66556ce9f2268a6188efb 0.600000000000 1530504 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": 1060043, "vin": [ { "gen": { "height": 1060033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db9bca1f31c9bdf3768c2993c1a8e3f5cba7e0ea85e66556ce9f2268a6188efb" } } ], "extra": [ 1, 126, 71, 78, 151, 147, 238, 166, 215, 52, 23, 27, 76, 179, 42, 205, 25, 121, 25, 59, 255, 159, 122, 115, 233, 122, 85, 252, 206, 183, 130, 13, 179, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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