Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fae74e10b55ab8d694cd02d5004b3e1c3a7bb79a704faba3b137554e69cf557

Tx prefix hash: f330228582b1cac6c147ed88f0696d2edcd541bd7972d85763d8d06ecc29d4ab
Tx public key: 3150198c19fede503e4be0c5234f8add1d843fd73618196a18b574ae44ea20b4
Timestamp: 1749381026 Timestamp [UCT]: 2025-06-08 11:10:26 Age [y:d:h:m:s]: 00:162:00:09:35
Block: 1300589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113467 RingCT/type: yes/0
Extra: 013150198c19fede503e4be0c5234f8add1d843fd73618196a18b574ae44ea20b4021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37fee2c02f6540ea6fd15c37fed04f202747666397afccecc5e6143977a952a5 0.600000000000 1788138 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": 1300599, "vin": [ { "gen": { "height": 1300589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37fee2c02f6540ea6fd15c37fed04f202747666397afccecc5e6143977a952a5" } } ], "extra": [ 1, 49, 80, 25, 140, 25, 254, 222, 80, 62, 75, 224, 197, 35, 79, 138, 221, 29, 132, 63, 215, 54, 24, 25, 106, 24, 181, 116, 174, 68, 234, 32, 180, 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