Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 488f53f3459f21668d3285b9bd2481e29af680ec3ad09dcef8ce83fd0eb51d56

Tx prefix hash: 887a15d5f1615a5b3b00416c0015c0208da8ea188e4f194d264d539cb8eaa6ba
Tx public key: 0c6a111ca67fe1c28469b1f56ed63f77307ad1e5595b421de7e7cef2756e334c
Timestamp: 1737663630 Timestamp [UCT]: 2025-01-23 20:20:30 Age [y:d:h:m:s]: 00:145:04:42:06
Block: 1203793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103511 RingCT/type: yes/0
Extra: 010c6a111ca67fe1c28469b1f56ed63f77307ad1e5595b421de7e7cef2756e334c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 194f48a060db5eaeb1041f67d6b954dd19a708351c00b70ab2f4201ac50e5d67 0.600000000000 1690472 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": 1203803, "vin": [ { "gen": { "height": 1203793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "194f48a060db5eaeb1041f67d6b954dd19a708351c00b70ab2f4201ac50e5d67" } } ], "extra": [ 1, 12, 106, 17, 28, 166, 127, 225, 194, 132, 105, 177, 245, 110, 214, 63, 119, 48, 122, 209, 229, 89, 91, 66, 29, 231, 231, 206, 242, 117, 110, 51, 76, 2, 17, 0, 0, 0, 2, 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