Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f7a75906ce706bd4082342a45bf09f12855491bf71d1e2a1f6f7c639f3abc75

Tx prefix hash: 19d8277ff90fec7263b689e20609fe38134959509cbace0ea10923dfee7505af
Tx public key: 6c691f3fead6fe4ac07629bf423939970ba85a3a6e9b5544db50bc8cbf9b86fd
Timestamp: 1693989495 Timestamp [UCT]: 2023-09-06 08:38:15 Age [y:d:h:m:s]: 01:132:17:27:48
Block: 842091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356194 RingCT/type: yes/0
Extra: 016c691f3fead6fe4ac07629bf423939970ba85a3a6e9b5544db50bc8cbf9b86fd021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.994984033000 dcy

stealth address amount amount idx
00: b405475046f2f8efc05a95bf8315c40b08990d022f31aace30fbf73a4473199d 0.994984033000 1295181 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": 842101, "vin": [ { "gen": { "height": 842091 } } ], "vout": [ { "amount": 994984033, "target": { "key": "b405475046f2f8efc05a95bf8315c40b08990d022f31aace30fbf73a4473199d" } } ], "extra": [ 1, 108, 105, 31, 63, 234, 214, 254, 74, 192, 118, 41, 191, 66, 57, 57, 151, 11, 168, 90, 58, 110, 155, 85, 68, 219, 80, 188, 140, 191, 155, 134, 253, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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