Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3783345bf67f8f64b537d2f73e8564c096cfe931ffd6e401131e7023160eaba

Tx prefix hash: d02b0c2226df6facf1205d679190366d8f765252c624bcee50033dd376b11eef
Tx public key: 9164d0f3e7b41364a30d748aa038062b918455b9128036365d24b623412270e9
Timestamp: 1703295093 Timestamp [UCT]: 2023-12-23 01:31:33 Age [y:d:h:m:s]: 01:318:04:10:07
Block: 919061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486226 RingCT/type: yes/0
Extra: 019164d0f3e7b41364a30d748aa038062b918455b9128036365d24b623412270e902110000000346113aa8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb5fe4528daec236c21d6e51d338d10bf299d33e7e51085c0cdd29b0e60a80df 0.600000000000 1376725 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": 919071, "vin": [ { "gen": { "height": 919061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb5fe4528daec236c21d6e51d338d10bf299d33e7e51085c0cdd29b0e60a80df" } } ], "extra": [ 1, 145, 100, 208, 243, 231, 180, 19, 100, 163, 13, 116, 138, 160, 56, 6, 43, 145, 132, 85, 185, 18, 128, 54, 54, 93, 36, 182, 35, 65, 34, 112, 233, 2, 17, 0, 0, 0, 3, 70, 17, 58, 168, 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