Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddcf39f9f1a7a076ab26ac2ae49d6588434c7781ba4f2579bc189d4b56a29245

Tx prefix hash: ebdffae7316a203fb5bad9ae191da529d9d5d11ecaf1c63f417d20819c20e380
Tx public key: b57595abcd14ed68e16f2d9347f6cd9ea210b56e254680baf1ba198976c182ea
Timestamp: 1740837185 Timestamp [UCT]: 2025-03-01 13:53:05 Age [y:d:h:m:s]: 00:338:00:19:48
Block: 1229838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239268 RingCT/type: yes/0
Extra: 01b57595abcd14ed68e16f2d9347f6cd9ea210b56e254680baf1ba198976c182ea02110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd67fe2c5f45de795915f854f1c3278d286c056f6a8067fb52d90bf0565e2be3 0.600000000000 1716729 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": 1229848, "vin": [ { "gen": { "height": 1229838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd67fe2c5f45de795915f854f1c3278d286c056f6a8067fb52d90bf0565e2be3" } } ], "extra": [ 1, 181, 117, 149, 171, 205, 20, 237, 104, 225, 111, 45, 147, 71, 246, 205, 158, 162, 16, 181, 110, 37, 70, 128, 186, 241, 186, 25, 137, 118, 193, 130, 234, 2, 17, 0, 0, 0, 13, 0, 127, 151, 138, 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