Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c5aa51e46a565aacbb535e5bd6cc0c8031ce5e3c303c00962e287a01db7484

Tx prefix hash: a486afb87ae69b05550d933a1126dde1b52bc463a4fa7e1c11ba6f040d4fb24c
Tx public key: 383c5b165f285c84507e5a91c800f588011b791bd4ec1dcb04e0060a0b147683
Timestamp: 1717277650 Timestamp [UCT]: 2024-06-01 21:34:10 Age [y:d:h:m:s]: 00:302:22:06:44
Block: 1035001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216477 RingCT/type: yes/0
Extra: 01383c5b165f285c84507e5a91c800f588011b791bd4ec1dcb04e0060a0b14768302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f4104e27e810d379334f0eba0b96a2ba3fd7eaa83b68f4759a55c90baa590f7 0.600000000000 1503520 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": 1035011, "vin": [ { "gen": { "height": 1035001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f4104e27e810d379334f0eba0b96a2ba3fd7eaa83b68f4759a55c90baa590f7" } } ], "extra": [ 1, 56, 60, 91, 22, 95, 40, 92, 132, 80, 126, 90, 145, 200, 0, 245, 136, 1, 27, 121, 27, 212, 236, 29, 203, 4, 224, 6, 10, 11, 20, 118, 131, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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