Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689a1b8b572ca1e890eebe6393f16236b6c7562d2e69c2ad0712e7a133039448

Tx prefix hash: 592b7db0d6421de24d259f0f358c309362e48f0c008c7c260fa5dee0c329e802
Tx public key: 3697b1b6932ca27b0eb46d79bef02e259fee897b19119e4b4dd3f26f5f17fd3d
Timestamp: 1737618390 Timestamp [UCT]: 2025-01-23 07:46:30 Age [y:d:h:m:s]: 00:150:13:17:42
Block: 1203427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107248 RingCT/type: yes/0
Extra: 013697b1b6932ca27b0eb46d79bef02e259fee897b19119e4b4dd3f26f5f17fd3d021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 321c7e4bd0d743bb78cd34f52a011c01710be24e2dc2ae739aab49f5fdfb86fd 0.600000000000 1690104 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": 1203437, "vin": [ { "gen": { "height": 1203427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "321c7e4bd0d743bb78cd34f52a011c01710be24e2dc2ae739aab49f5fdfb86fd" } } ], "extra": [ 1, 54, 151, 177, 182, 147, 44, 162, 123, 14, 180, 109, 121, 190, 240, 46, 37, 159, 238, 137, 123, 25, 17, 158, 75, 77, 211, 242, 111, 95, 23, 253, 61, 2, 17, 0, 0, 0, 9, 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