Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f9af99cb02c6f4c1d711e4099331ee0d9036d6811941979230c99795a49b80

Tx prefix hash: eb605f7dd13a54f7731ee897fc758712e385adc84ac808515682a871f1484296
Tx public key: 062fc697c7c37f5a1b86d6823dfcded183e1a9f096c037f70434c44687dd81e8
Timestamp: 1721222966 Timestamp [UCT]: 2024-07-17 13:29:26 Age [y:d:h:m:s]: 00:258:00:35:33
Block: 1067709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184309 RingCT/type: yes/0
Extra: 01062fc697c7c37f5a1b86d6823dfcded183e1a9f096c037f70434c44687dd81e802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4eab3d58d22a1ff06de686e959fc1a0e7099f1065345b05e3fab47e14b41b62 0.600000000000 1538594 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": 1067719, "vin": [ { "gen": { "height": 1067709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4eab3d58d22a1ff06de686e959fc1a0e7099f1065345b05e3fab47e14b41b62" } } ], "extra": [ 1, 6, 47, 198, 151, 199, 195, 127, 90, 27, 134, 214, 130, 61, 252, 222, 209, 131, 225, 169, 240, 150, 192, 55, 247, 4, 52, 196, 70, 135, 221, 129, 232, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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