Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd98844f48b9a703f86ebad1d8e1559e7dbda189725808fbdf8893c2824a8c99

Tx prefix hash: 666fc41af154758272a6ba953472cea0960c0e77efed4dce2f0c5d29d92e2bd8
Tx public key: 4e03993c3b63fd573f55b75f34c272f23351d9f429d05526c55ee9aceeadf1cd
Timestamp: 1740891786 Timestamp [UCT]: 2025-03-02 05:03:06 Age [y:d:h:m:s]: 00:263:19:18:10
Block: 1230290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186288 RingCT/type: yes/0
Extra: 014e03993c3b63fd573f55b75f34c272f23351d9f429d05526c55ee9aceeadf1cd02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 487a97d80693887e2034cfe9e2191805900241a538fe6a5f3666e725e519c3fa 0.600000000000 1717187 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": 1230300, "vin": [ { "gen": { "height": 1230290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "487a97d80693887e2034cfe9e2191805900241a538fe6a5f3666e725e519c3fa" } } ], "extra": [ 1, 78, 3, 153, 60, 59, 99, 253, 87, 63, 85, 183, 95, 52, 194, 114, 242, 51, 81, 217, 244, 41, 208, 85, 38, 197, 94, 233, 172, 238, 173, 241, 205, 2, 17, 0, 0, 0, 10, 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