Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b672f786e38ce22c97eb5a6ad2344b69915e9a408b000da959321f3d93b1e2e

Tx prefix hash: 539edc5b210ca20e9101f99106562a23786a6fa61e662dabd9ce1c9c3b350b69
Tx public key: 4a8794b2f82139331454736b36297965435e57091b1a3d1a05a883cb95d46a13
Timestamp: 1745836869 Timestamp [UCT]: 2025-04-28 10:41:09 Age [y:d:h:m:s]: 00:014:09:58:33
Block: 1271242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10305 RingCT/type: yes/0
Extra: 014a8794b2f82139331454736b36297965435e57091b1a3d1a05a883cb95d46a1302110000000b1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f013ecb96841c5f339f40d0718d2127b43cb3ca1d69d2de27433797e0ee51b7f 0.600000000000 1758497 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": 1271252, "vin": [ { "gen": { "height": 1271242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f013ecb96841c5f339f40d0718d2127b43cb3ca1d69d2de27433797e0ee51b7f" } } ], "extra": [ 1, 74, 135, 148, 178, 248, 33, 57, 51, 20, 84, 115, 107, 54, 41, 121, 101, 67, 94, 87, 9, 27, 26, 61, 26, 5, 168, 131, 203, 149, 212, 106, 19, 2, 17, 0, 0, 0, 11, 31, 144, 81, 122, 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