Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5ba51d83c831edb48daff715d124e2d132660caaa439c5d2a16cc4f0472480

Tx prefix hash: b8067802df8cbc78e0ac910a4cdd5d2f5d1fde439ccd74cb324dfabd4fe166dc
Tx public key: 64b8fd874ca3cc936e9405b55507879ec141c64eef5c21940c5e717b1b321124
Timestamp: 1710707165 Timestamp [UCT]: 2024-03-17 20:26:05 Age [y:d:h:m:s]: 00:313:02:28:42
Block: 980534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224056 RingCT/type: yes/0
Extra: 0164b8fd874ca3cc936e9405b55507879ec141c64eef5c21940c5e717b1b321124021100000002a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e65f7a26aaa359cf38f7ce3681bd611e9d184df559a7a5a467d388252fe0570 0.600000000000 1440609 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": 980544, "vin": [ { "gen": { "height": 980534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e65f7a26aaa359cf38f7ce3681bd611e9d184df559a7a5a467d388252fe0570" } } ], "extra": [ 1, 100, 184, 253, 135, 76, 163, 204, 147, 110, 148, 5, 181, 85, 7, 135, 158, 193, 65, 198, 78, 239, 92, 33, 148, 12, 94, 113, 123, 27, 50, 17, 36, 2, 17, 0, 0, 0, 2, 165, 223, 157, 134, 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