Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d815715708e805497dd2851c85c95a26f8df77959a0af6a8e0b3000e53f1ddf

Tx prefix hash: 1866c3c0d0d22ef2f11db97df67f6697d17b0c4b336980ac51d6a4d80919c56f
Tx public key: 04cf71907ceba315df2c1e64ecb44ad2e7c383253c29d6e1160ef89a685cc4b6
Timestamp: 1745692110 Timestamp [UCT]: 2025-04-26 18:28:30 Age [y:d:h:m:s]: 00:206:19:46:21
Block: 1270049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145522 RingCT/type: yes/0
Extra: 0104cf71907ceba315df2c1e64ecb44ad2e7c383253c29d6e1160ef89a685cc4b602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d67195c0248f73ba47e3571a553cbd7544f805b7efacda86134e8c68b494c34 0.600000000000 1757290 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": 1270059, "vin": [ { "gen": { "height": 1270049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d67195c0248f73ba47e3571a553cbd7544f805b7efacda86134e8c68b494c34" } } ], "extra": [ 1, 4, 207, 113, 144, 124, 235, 163, 21, 223, 44, 30, 100, 236, 180, 74, 210, 231, 195, 131, 37, 60, 41, 214, 225, 22, 14, 248, 154, 104, 92, 196, 182, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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