Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce89b13e94892848a6013391bab4f14558b2bbf232c820e37556ca7cabe023ef

Tx prefix hash: 5bf3dbf5cc0a4ffe5fb408adbea6cc0f00a4d067284395739f2bb0e5f3cf02c5
Tx public key: 932a68a791320f6d555b8fd993d7de63a060b02ac4e5094ce763763fe550505b
Timestamp: 1698063396 Timestamp [UCT]: 2023-10-23 12:16:36 Age [y:d:h:m:s]: 01:091:20:47:24
Block: 875895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326851 RingCT/type: yes/0
Extra: 01932a68a791320f6d555b8fd993d7de63a060b02ac4e5094ce763763fe550505b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.768769743000 dcy

stealth address amount amount idx
00: 6339f4ce09dad7eec282dd711205b39af9c29924a1da45f0bef2e8ed0ac31573 0.768769743000 1331189 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": 875905, "vin": [ { "gen": { "height": 875895 } } ], "vout": [ { "amount": 768769743, "target": { "key": "6339f4ce09dad7eec282dd711205b39af9c29924a1da45f0bef2e8ed0ac31573" } } ], "extra": [ 1, 147, 42, 104, 167, 145, 50, 15, 109, 85, 91, 143, 217, 147, 215, 222, 99, 160, 96, 176, 42, 196, 229, 9, 76, 231, 99, 118, 63, 229, 80, 80, 91, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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