Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda66689ab65fd851fa920c366c318737c4de30a6d2517adec51fdd9a3024eef

Tx prefix hash: a5ed2d56de7494bfbbc4d5f0a51eb3ddf33bdf905a8cee8d5b886c0a6fb5f58d
Tx public key: ddaee14da6c7c5e64306848f8ef4d98556cb1b0a0260cbb15ff27ef53f574418
Timestamp: 1734521719 Timestamp [UCT]: 2024-12-18 11:35:19 Age [y:d:h:m:s]: 00:105:15:57:20
Block: 1177865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75264 RingCT/type: yes/0
Extra: 01ddaee14da6c7c5e64306848f8ef4d98556cb1b0a0260cbb15ff27ef53f5744180211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b50fc82b4d41ede3f4d19c4382dd36b044010cffd82cf5809c63c2728c45aaaf 0.600000000000 1664244 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": 1177875, "vin": [ { "gen": { "height": 1177865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b50fc82b4d41ede3f4d19c4382dd36b044010cffd82cf5809c63c2728c45aaaf" } } ], "extra": [ 1, 221, 174, 225, 77, 166, 199, 197, 230, 67, 6, 132, 143, 142, 244, 217, 133, 86, 203, 27, 10, 2, 96, 203, 177, 95, 242, 126, 245, 63, 87, 68, 24, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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