Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 744f8d378529b571bd6ef23ca59a9cf3c527e666d36422b5e7863d0713c38117

Tx prefix hash: 9d2d15eef2ff0bb2d140d9cd67e451f46f2533f0a219971e6861090490130f9e
Tx public key: 65c1e4b137aac9d84eb973db35cfbfac1c06ee44ec11fa7b5f3bb49f5140d622
Timestamp: 1688400191 Timestamp [UCT]: 2023-07-03 16:03:11 Age [y:d:h:m:s]: 01:345:13:18:23
Block: 795835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508099 RingCT/type: yes/0
Extra: 0165c1e4b137aac9d84eb973db35cfbfac1c06ee44ec11fa7b5f3bb49f5140d62202110000000475e3f0e9000000000000000000

1 output(s) for total of 1.416016827000 dcy

stealth address amount amount idx
00: e4b6dcfc281e9cf6e8eebd875381718c860bdd5c13ec40f7c96443464286005d 1.416016827000 1246672 of 0

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": 795845, "vin": [ { "gen": { "height": 795835 } } ], "vout": [ { "amount": 1416016827, "target": { "key": "e4b6dcfc281e9cf6e8eebd875381718c860bdd5c13ec40f7c96443464286005d" } } ], "extra": [ 1, 101, 193, 228, 177, 55, 170, 201, 216, 78, 185, 115, 219, 53, 207, 191, 172, 28, 6, 238, 68, 236, 17, 250, 123, 95, 59, 180, 159, 81, 64, 214, 34, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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