Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4a8d5f5d473f42d60df6385aff392f3a3dede50a606d427d650384ae82fef0

Tx prefix hash: dae8879530eee5daa6b417e02c8fb8c427587ab423efb3fba3dfef77ddd709e7
Tx public key: c13ccee6c27b7b13474cabc3b43187d64b5bfaba06638ea92b37f3dc01e431c6
Timestamp: 1705101071 Timestamp [UCT]: 2024-01-12 23:11:11 Age [y:d:h:m:s]: 01:303:01:22:18
Block: 934023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475422 RingCT/type: yes/0
Extra: 01c13ccee6c27b7b13474cabc3b43187d64b5bfaba06638ea92b37f3dc01e431c602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ac093257dd36c8c335bf7263989a7a08362267b816bd814c32c9125b391768a 0.600000000000 1392009 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": 934033, "vin": [ { "gen": { "height": 934023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ac093257dd36c8c335bf7263989a7a08362267b816bd814c32c9125b391768a" } } ], "extra": [ 1, 193, 60, 206, 230, 194, 123, 123, 19, 71, 76, 171, 195, 180, 49, 135, 214, 75, 91, 250, 186, 6, 99, 142, 169, 43, 55, 243, 220, 1, 228, 49, 198, 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