Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce4f2d290a9a980d61d0b087041d7480ca078c2ee23d00767c97f5134e5058c9

Tx prefix hash: 989df311b8277e01277f02afc6b4876c7c68b8ea2924cc3256d744fe33e28ee1
Tx public key: bfc54f9efbb932b1c509411134039bed815d2ae79097b85bc00a49d2d1b1ad24
Timestamp: 1708465321 Timestamp [UCT]: 2024-02-20 21:42:01 Age [y:d:h:m:s]: 01:043:21:21:43
Block: 961927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292389 RingCT/type: yes/0
Extra: 01bfc54f9efbb932b1c509411134039bed815d2ae79097b85bc00a49d2d1b1ad240211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c14455735c56b3c0b7bf455714f6df0aaa660d8422302ed2b3afe9f0dc576e71 0.600000000000 1421544 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": 961937, "vin": [ { "gen": { "height": 961927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c14455735c56b3c0b7bf455714f6df0aaa660d8422302ed2b3afe9f0dc576e71" } } ], "extra": [ 1, 191, 197, 79, 158, 251, 185, 50, 177, 197, 9, 65, 17, 52, 3, 155, 237, 129, 93, 42, 231, 144, 151, 184, 91, 192, 10, 73, 210, 209, 177, 173, 36, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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