Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9260fe59f58e0e58ac20813340086fdf27611f11d6a2da8c7cbf0e5a572288e

Tx prefix hash: 75711e7a9cb691eab4f8198f20f26639c1744b0eac9193b8e9b2585c1012c38b
Tx public key: ec9284363ec6e1778344016a2a2525c8beafb2ff3f57e1c20924a080e41c26dd
Timestamp: 1702520915 Timestamp [UCT]: 2023-12-14 02:28:35 Age [y:d:h:m:s]: 01:331:16:27:18
Block: 912643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495912 RingCT/type: yes/0
Extra: 01ec9284363ec6e1778344016a2a2525c8beafb2ff3f57e1c20924a080e41c26dd02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1660713cf0ab962bc8937e4932e022e52a4a6e25c1b388e14ee6de58ada6e030 0.600000000000 1369875 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": 912653, "vin": [ { "gen": { "height": 912643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1660713cf0ab962bc8937e4932e022e52a4a6e25c1b388e14ee6de58ada6e030" } } ], "extra": [ 1, 236, 146, 132, 54, 62, 198, 225, 119, 131, 68, 1, 106, 42, 37, 37, 200, 190, 175, 178, 255, 63, 87, 225, 194, 9, 36, 160, 128, 228, 28, 38, 221, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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