Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e826ef2e0f0f239e2ae1889533c87806b085d6de4ad9a18bec2a248ea3d6515

Tx prefix hash: b988bb997f3969b94f2bdf5db6cd0f1cc9d56a81890116fdfb02ef38e8ae1220
Tx public key: 99cd14fc5413af783aacdb7a3e05c523d2bf3b4482b8b7e6f2d93189089233ba
Timestamp: 1749317704 Timestamp [UCT]: 2025-06-07 17:35:04 Age [y:d:h:m:s]: 00:159:14:10:01
Block: 1300072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111737 RingCT/type: yes/0
Extra: 0199cd14fc5413af783aacdb7a3e05c523d2bf3b4482b8b7e6f2d93189089233ba021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 410ea18f73071cb99c01fecb0d2cac30332003116d6bc04c8957b3242633f487 0.600000000000 1787619 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": 1300082, "vin": [ { "gen": { "height": 1300072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "410ea18f73071cb99c01fecb0d2cac30332003116d6bc04c8957b3242633f487" } } ], "extra": [ 1, 153, 205, 20, 252, 84, 19, 175, 120, 58, 172, 219, 122, 62, 5, 197, 35, 210, 191, 59, 68, 130, 184, 183, 230, 242, 217, 49, 137, 8, 146, 51, 186, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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