Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 678b15c432d601be64afbeb9093a9ad7c2027af0a0b8b03d713959dddf2cc263

Tx prefix hash: 7f0db4d4f82911bd22526c384f36e75e3d1ccb6b84df4a14d66b1ad4b5cdfaac
Tx public key: 7965b0720dd624cd9097c2f8b0cc203bf48f1ad2640d00699e0fcfb0788b5923
Timestamp: 1743692356 Timestamp [UCT]: 2025-04-03 14:59:16 Age [y:d:h:m:s]: 00:179:03:52:32
Block: 1253480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125705 RingCT/type: yes/0
Extra: 017965b0720dd624cd9097c2f8b0cc203bf48f1ad2640d00699e0fcfb0788b5923021100000004a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62d5aadd926cbd90ceeb1383dc344411fca26088a4d33f576d5d06c20c06fd27 0.600000000000 1740561 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": 1253490, "vin": [ { "gen": { "height": 1253480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62d5aadd926cbd90ceeb1383dc344411fca26088a4d33f576d5d06c20c06fd27" } } ], "extra": [ 1, 121, 101, 176, 114, 13, 214, 36, 205, 144, 151, 194, 248, 176, 204, 32, 59, 244, 143, 26, 210, 100, 13, 0, 105, 158, 15, 207, 176, 120, 139, 89, 35, 2, 17, 0, 0, 0, 4, 162, 237, 1, 107, 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